Learn Build status updates of commit 04d785a:

✅ Validation status: passed

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

@Evvn : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Learn Build status updates of commit 4314a5d:

✅ Validation status: passed

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

PRMerger Results

@Evvn,
Thanks for your contribution! For the new image, instead of blurring, can you obscure the sensitive information by using an opaque color block the same color as the background or by replacing the information with fictitious information?

@jeevansd

Can you review the proposed changes? Note that the new image needs to be updated before merging.

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Learn Build status updates of commit 3dd6e11:

✅ Validation status: passed

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

PRMerger Results

@Evvn, Thanks for your contribution! For the new image, instead of blurring, can you obscure the sensitive information by using an opaque color block the same color as the background or by replacing the information with fictitious information?

Thank you for the review, I've replaced the image using the proposed opaque blocks with the same color as the background instead of a mosaic blur.

#sign-off

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @jeevansd

#sign-off

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @jeevansd

@jeevansd

Can you review the proposed changes? Note that the new image needs to be updated before merging.

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

@Court72 just coming back to this as it's been sitting for ~1 month now, is there anything I can do to get this merged? It's helpful for our troubleshooting if our customers follow the updated steps from this PR, so I don't want to wait too long if possible.

I reached out to the author on Teams today.

#sign-off